fix @paralleldrive/cuid2 to 2.2.2#1055
Merged
tunnckoCore merged 1 commit intonode-formidable:masterfrom Feb 18, 2026
Merged
Conversation
…w engine requirements
Member
|
@RampouchCZ ah, yeah, sorry about that. we'll merge soon |
tunnckoCore
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
currently formidable uses
"@paralleldrive/cuid2": "^2.2.2"which since last week pulls version2.3.0with sub-dependency"@noble/hashes": "2.0.1". This new version of@noble/hasheshas new nodejs engine requirements>= 20.19.0which is incompatible with formidable's>=14.0.0.This is currently breaking our builds as we have to manually add resolutions all over the place to address this.